SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
 
Tags
    Impact
      Clean code attribute
        1. Using unsafe code blocks is security-sensitive

           Security Hotspot
        2. Not specifying a timeout for regular expressions is security-sensitive

           Security Hotspot
        3. Hard-coded secrets are security-sensitive

           Security Hotspot
        4. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        5. Deserializing objects without performing data validation is security-sensitive

           Security Hotspot
        6. Disabling ASP.NET "Request Validation" feature is security-sensitive

           Security Hotspot
        7. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        8. Using publicly writable directories is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        11. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        12. Configuring loggers is security-sensitive

           Security Hotspot
        13. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        14. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        15. Disabling CSRF protections is security-sensitive

           Security Hotspot
        16. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        17. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        18. Setting loose file permissions is security-sensitive

           Security Hotspot
        19. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        20. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        21. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        22. Formatting SQL queries is security-sensitive

           Security Hotspot
        23. Hard-coded credentials are security-sensitive

           Security Hotspot
        24. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Constructing arguments of system commands from user input is security-sensitive

        intentionality - logical
        security
        Security Hotspot
        • cwe
        • injection

        Constructing arguments of system commands from user input is security-sensitive. It has led in the past to the following vulnerabilities:

        • CVE-2016-9920
        • CVE-2021-29472

        Arguments of system commands are processed by the executed program. The arguments are usually used to configure and influence the behavior of the programs. Control over a single argument might be enough for an attacker to trigger dangerous features like executing arbitrary commands or writing files into specific directories.

        Ask Yourself Whether

        • Malicious arguments can result in undesired behavior in the executed command.
        • Passing user input to a system command is not necessary.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Avoid constructing system commands from user input when possible.
        • Ensure that no risky arguments can be injected for the given program, e.g., type-cast the argument to an integer.
        • Use a more secure interface to communicate with other programs, e.g., the standard input stream (stdin).

        Sensitive Code Example

        Arguments like -delete or -exec for the find command can alter the expected behavior and result in vulnerabilities:

        using System.Diagnostics;
        Process p = new Process();
        p.StartInfo.FileName = "/usr/bin/find";
        p.StartInfo.ArgumentList.Add(input); // Sensitive
        

        Compliant Solution

        Use an allow-list to restrict the arguments to trusted values:

        using System.Diagnostics;
        Process p = new Process();
        p.StartInfo.FileName = "/usr/bin/find";
        if (allowed.Contains(input)) {
          p.StartInfo.ArgumentList.Add(input);
        }
        

        See

        • OWASP - Top 10 2021 Category A3 - Injection
        • OWASP - Top 10 2017 Category A1 - Injection
        • CWE - CWE-88 - Argument Injection or Modification
        • CVE-2021-29472 - PHP Supply Chain Attack on Composer
        • STIG Viewer - Application Security and Development: V-222609 - The application must not be subject to input handling vulnerabilities.
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.2

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use